What's New in 12.2.0.0

Configure Requirement Status based on Requirement Screen

Users can configure relevant statuses for requirements based on different requirement screen like Policy Requirement screen or Application Requirement Screen or Client Requirement screen. Users can now sort the requirements table on the Activity Level screen.

These statuses can be configured in below AsCode. These values must be configured by the user if the user needs different Requirement Statuses per screen. If these codes are not configured then all the statuses will get displayed in the Requirement Status Combo and Edit requirement option.

  • Policy Requirement: Users can configure only statuses that are relevant to Policy requirement screen using AsCodePolicyRequirementStatus.

  • Application Requirement: Users can configure only statuses that are relevant to Application requirement screen using AsCodeApplicationRequirementStatus.

  • Activity Requirement: Users can configure only statuses that are relevant to Activity requirement screen AsCodeActivityRequirementStatus.

  • Client Requirement: Users can configure only statuses that are relevant to Client requirement screen AsCodeClientRequirementStatus.

Principal-First Repayment Option for Fixed Funds – Non-Proportional Reduction

OIPA introduces a new Non-Proportional Reduction repayment option for newly created Fixed Funds. This new plan-fund level configuration allows administrators to choose between the existing proportional principal reduction method and a new Principal-First non-proportional reduction method for policy loan repayments and removals. The non-proportional reduction feature applies only to fixed funds.

When enabled, loan repayments reduce principal directly by the repayment amount without proportional scaling, while existing interest accrual, capitalization timing, and capitalization processing behavior remain unchanged.

By default, OIPA continues to use the existing proportional repayment logic unless the Non-Proportional Reduction option is explicitly configured.

Show or Hide Inquiry Screen Result Tabs

A new optional SHOW attribute is now supported on the <Result> element in the InquiryScreen business rule. This enhancement allows InquiryScreen result tabs to be dynamically shown or hidden based on ScreenMath business conditions evaluated during screen lifecycle events.

Requirement History Tracking for Business Rules

OIPA now records history for requirements and activities added or updated through attached business rules processed through activities. Previously, history was captured only for changes made through the OIPA UI. Users can now view client-level requirement history in the Client Requirement History tab.

The complete change history can be viewed from the History tab on the Requirement screen. History details are stored in the AsHistory and AsHistoryDetail tables.

Inquiry Screen Auto-Refresh Enhancement

Inquiry screens now support automatic result refresh for configured Combo drop-down fields using the SUBMITFORM and FIELD attributes. When enabled, Inquiry results reload automatically upon drop-down selection changes, reducing manual clicks and improving navigation efficiency while preserving existing Inquiry behavior and compatibility.